Skip to main content

This is a new service – your feedback will help us to improve it.

London Borough of Lewisham

Article 4 direction area

There is a problem

  • 78 issue of type invalid category value

Perry Vale Parade

reference
Per2
name
Perry Vale Parade
article-4-direction
permitted-development-rights

undefined

Class e
uprns
address-texts
geometry
MULTIPOLYGON (((-0.044211 51.435349,-0.044207 51.435341,-0.044093 51.435350,-0.044079 51.435362,-0.044151 51.435482,-0.044144 51.435482,-0.044152 51.435525,-0.044163 51.435523,-0.044181 51.435571,-0.044215 51.435562,-0.044203 51.435520,-0.044234 51.435518,-0.044211 51.435349)),((-0.043860 51.435438,-0.043809 51.435360,-0.043574 51.435356,-0.043602 51.435442,-0.043723 51.435439,-0.043724 51.435457,-0.043743 51.435456,-0.043744 51.435441,-0.043820 51.435439,-0.043819 51.435458,-0.043838 51.435458,-0.043839 51.435440,-0.043860 51.435438)),((-0.043269 51.435347,-0.043265 51.435513,-0.043350 51.435514,-0.043353 51.435452,-0.043505 51.435459,-0.043515 51.435448,-0.043521 51.435355,-0.043269 51.435347)),((-0.043816 51.435024,-0.043822 51.435063,-0.043797 51.435065,-0.043800 51.435093,-0.043751 51.435096,-0.043733 51.435032,-0.043632 51.435034,-0.043644 51.435097,-0.043618 51.435106,-0.043589 51.434999,-0.043507 51.435004,-0.043546 51.435181,-0.043951 51.435164,-0.043912 51.435015,-0.043816 51.435024)))
point
POINT (-0.043707 51.435281)
notes
entry-date
2026-02-25
start-date
end-date

How to fix this issue

Your data is missing a permitted-development-rights.

The Article 4 direction area guidance explains how to fix the issue:

permitted-development-rights

A list of the permitted development rights withdrawn by the article 4 direction.

Separate the rights in the list using semicolons.

Only use rights from our permitted development right dataset. If the area withdraws a permitted development right that is not in our dataset, email digitalland@communities.gov.uk.

Example: 3D;3M;11B

How to improve London Borough of Lewisham’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL